fix: wire SSR route components - #728

Summary

create-croco-app SSR route templates now pass the generated page component value into defineRoute(), so container-fullstack and ssr-lambda apps no longer emit route definitions backed by undefined casts or type-only runtime references.

Fixes #694

변경 사항

• Import the generated page component as a value in both SSR route templates and assign it directly to component.
• Keep route object type validation with satisfies PageRouteDefinition before calling defineRoute().
• Export the existing CrocoDataFn type from @croco/frontend-react so the SSR Lambda fixture typechecks through the public package entrypoint.
• Add template and public type regressions plus patch changesets for create-croco-app and @croco/frontend-react.

Verification

• pnpm --filter create-croco-app exec vitest run src/tests/templates-build.spec.ts
• pnpm --filter create-croco-app test (7 files, 30 tests)
• pnpm --filter create-croco-app typecheck
• pnpm --filter create-croco-app build
• TypeScript compiler API route smoke for both SSR route files, both Page components, and ssr-lambda pageData.ts
• pnpm --filter @croco/frontend-react test (2 files, 5 tests)
• pnpm --filter @croco/frontend-react typecheck
• pnpm --filter @croco/frontend-react build
• pnpm check
• git diff --check origin/trunk..HEAD
• pnpm exec changeset status --since origin/trunk
• pre-push: auto-changeset, full pnpm test (195 tasks), full pnpm typecheck (194 tasks)

Self-review

• Correctness/regression: [create-croco-app] SSR 라우트 템플릿이 컴포넌트 값을 잘못 연결함 #694 acceptance is covered by template assertions that reject type-only default imports, component: undefined, and the old Page satisfies Page runtime pattern; the route smoke typechecks both templates with the generated Page value and pageData.ts.
• API/security/compatibility/release: CrocoDataFn is an additive public type export for a type already defined in @croco/frontend-react; no runtime dependencies, lockfile entries, environment assumptions, or secrets changed. Patch changesets cover both publishable packages.
• Maintainability/minimality: the runtime/template diff is limited to the two affected route files and one existing public type barrel; tests are focused on the regression and no new abstraction or unrelated cleanup was introduced.

Risk

Low. The route templates now reference the existing generated component value directly; the only public API surface change is an additive type export used by the existing SSR template fixture.